|
Server : Apache System : Linux server.mata-lashes.com 3.10.0-1160.90.1.el7.x86_64 #1 SMP Thu May 4 15:21:22 UTC 2023 x86_64 User : matalashes ( 1004) PHP Version : 8.1.29 Disable Function : NONE Directory : /usr/share/selinux/devel/html/ |
Upload File : |
<!-- Creator : groff version 1.22.2 -->
<!-- CreationDate: Mon Nov 16 16:50:41 2020 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta name="generator" content="groff -Thtml, see www.gnu.org">
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<meta name="Content-Style" content="text/css">
<style type="text/css">
p { margin-top: 0; margin-bottom: 0; vertical-align: top }
pre { margin-top: 0; margin-bottom: 0; vertical-align: top }
table { margin-top: 0; margin-bottom: 0; vertical-align: top }
h1 { text-align: center }
</style>
<title>sanlock_selinux</title>
</head>
<body>
<h1 align="center">sanlock_selinux</h1>
<a href="#NAME">NAME</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#ENTRYPOINTS">ENTRYPOINTS</a><br>
<a href="#PROCESS TYPES">PROCESS TYPES</a><br>
<a href="#BOOLEANS">BOOLEANS</a><br>
<a href="#MANAGED FILES">MANAGED FILES</a><br>
<a href="#FILE CONTEXTS">FILE CONTEXTS</a><br>
<a href="#COMMANDS">COMMANDS</a><br>
<a href="#AUTHOR">AUTHOR</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>
<hr>
<h2>NAME
<a name="NAME"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">sanlock_selinux
− Security Enhanced Linux Policy for the sanlock
processes</p>
<h2>DESCRIPTION
<a name="DESCRIPTION"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Security-Enhanced
Linux secures the sanlock processes via flexible mandatory
access control.</p>
<p style="margin-left:11%; margin-top: 1em">The sanlock
processes execute with the sanlock_t SELinux type. You can
check if you have these processes running by executing the
<b>ps</b> command with the <b>−Z</b> qualifier.</p>
<p style="margin-left:11%; margin-top: 1em">For
example:</p>
<p style="margin-left:11%; margin-top: 1em"><b>ps -eZ |
grep sanlock_t</b></p>
<h2>ENTRYPOINTS
<a name="ENTRYPOINTS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">The sanlock_t
SELinux type can be entered via the <b>sanlock_exec_t</b>
file type.</p>
<p style="margin-left:11%; margin-top: 1em">The default
entrypoint paths for the sanlock_t domain are the
following:</p>
<p style="margin-left:11%; margin-top: 1em">/usr/sbin/sanlock</p>
<h2>PROCESS TYPES
<a name="PROCESS TYPES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">SELinux defines
process types (domains) for each process running on the
system</p>
<p style="margin-left:11%; margin-top: 1em">You can see the
context of a process using the <b>−Z</b> option to
<b>ps</b></p>
<p style="margin-left:11%; margin-top: 1em">Policy governs
the access confined processes have to files. SELinux sanlock
policy is very flexible allowing users to setup their
sanlock processes in as secure a method as possible.</p>
<p style="margin-left:11%; margin-top: 1em">The following
process types are defined for sanlock:</p>
<p style="margin-left:11%; margin-top: 1em"><b>sanlock_t</b></p>
<p style="margin-left:11%; margin-top: 1em">Note:
<b>semanage permissive -a sanlock_t</b> can be used to make
the process type sanlock_t permissive. SELinux does not deny
access to permissive process types, but the AVC (SELinux
denials) messages are still generated.</p>
<h2>BOOLEANS
<a name="BOOLEANS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">SELinux policy
is customizable based on least access required. sanlock
policy is extremely flexible and has several booleans that
allow you to manipulate the policy and run sanlock with the
tightest access possible.</p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow sanlock to read/write user home directories, you must
turn on the sanlock_enable_home_dirs boolean. Disabled by
default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
sanlock_enable_home_dirs 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow sanlock to read/write fuse files, you must turn on the
sanlock_use_fusefs boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
sanlock_use_fusefs 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow sanlock to manage nfs files, you must turn on the
sanlock_use_nfs boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
sanlock_use_nfs 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow sanlock to manage cifs files, you must turn on the
sanlock_use_samba boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
sanlock_use_samba 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow users to resolve user passwd entries directly from
ldap rather then using a sssd server, you must turn on the
authlogin_nsswitch_use_ldap boolean. Disabled by
default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
authlogin_nsswitch_use_ldap 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow all daemons to write corefiles to /, you must turn on
the daemons_dump_core boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
daemons_dump_core 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
enable cluster mode for daemons, you must turn on the
daemons_enable_cluster_mode boolean. Enabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
daemons_enable_cluster_mode 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow all daemons to use tcp wrappers, you must turn on the
daemons_use_tcp_wrapper boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
daemons_use_tcp_wrapper 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow all daemons the ability to read/write terminals, you
must turn on the daemons_use_tty boolean. Disabled by
default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
daemons_use_tty 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
deny any process from ptracing or debugging any other
processes, you must turn on the deny_ptrace boolean. Enabled
by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
deny_ptrace 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow any process to mmap any file on system with attribute
file_type, you must turn on the domain_can_mmap_files
boolean. Enabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
domain_can_mmap_files 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow all domains write to kmsg_device, while kernel is
executed with systemd.log_target=kmsg parameter, you must
turn on the domain_can_write_kmsg boolean. Disabled by
default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
domain_can_write_kmsg 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow all domains to use other domains file descriptors, you
must turn on the domain_fd_use boolean. Enabled by
default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
domain_fd_use 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow all domains to have the kernel load modules, you must
turn on the domain_kernel_load_modules boolean. Disabled by
default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
domain_kernel_load_modules 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow all domains to execute in fips_mode, you must turn on
the fips_mode boolean. Enabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
fips_mode 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
enable reading of urandom for all domains, you must turn on
the global_ssp boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
global_ssp 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow confined applications to run with kerberos, you must
turn on the kerberos_enabled boolean. Enabled by
default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
kerberos_enabled 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow system to run with NIS, you must turn on the
nis_enabled boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
nis_enabled 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow confined applications to use nscd shared memory, you
must turn on the nscd_use_shm boolean. Disabled by
default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
nscd_use_shm 1</b></p>
<h2>MANAGED FILES
<a name="MANAGED FILES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">The SELinux
process type sanlock_t can manage files labeled with the
following file types. The paths listed are the default paths
for these file types. Note the processes UID still need to
have DAC permissions.</p>
<p style="margin-left:11%; margin-top: 1em"><b>cephfs_t</b></p>
<p style="margin-left:11%; margin-top: 1em"><b>cifs_t</b></p>
<p style="margin-left:11%; margin-top: 1em"><b>cluster_conf_t</b></p>
<p style="margin-left:11%; margin-top: 1em">/etc/cluster(/.*)?</p>
<p style="margin-left:11%; margin-top: 1em"><b>cluster_var_lib_t</b></p>
<p style="margin-left:11%; margin-top: 1em">/var/lib/pcsd(/.*)?
<br>
/var/lib/cluster(/.*)? <br>
/var/lib/openais(/.*)? <br>
/var/lib/pengine(/.*)? <br>
/var/lib/corosync(/.*)? <br>
/usr/lib/heartbeat(/.*)? <br>
/var/lib/heartbeat(/.*)? <br>
/var/lib/pacemaker(/.*)?</p>
<p style="margin-left:11%; margin-top: 1em"><b>cluster_var_run_t</b></p>
<p style="margin-left:11%; margin-top: 1em">/var/run/crm(/.*)?
<br>
/var/run/cman_.* <br>
/var/run/rsctmp(/.*)? <br>
/var/run/aisexec.* <br>
/var/run/heartbeat(/.*)? <br>
/var/run/corosync-qnetd(/.*)? <br>
/var/run/corosync-qdevice(/.*)? <br>
/var/run/cpglockd.pid <br>
/var/run/corosync.pid <br>
/var/run/rgmanager.pid <br>
/var/run/cluster/rgmanager.sk</p>
<p style="margin-left:11%; margin-top: 1em"><b>fusefs_t</b></p>
<p style="margin-left:11%; margin-top: 1em">/var/run/user/[^/]*/gvfs</p>
<p style="margin-left:11%; margin-top: 1em"><b>nfs_t</b></p>
<p style="margin-left:11%; margin-top: 1em"><b>root_t</b></p>
<p style="margin-left:11%; margin-top: 1em">/sysroot/ostree/deploy/.*-atomic.*/deploy(/.*)?
<br>
/ <br>
/initrd</p>
<p style="margin-left:11%; margin-top: 1em"><b>sanlock_conf_t</b></p>
<p style="margin-left:11%; margin-top: 1em">/etc/sanlock(/.*)?</p>
<p style="margin-left:11%; margin-top: 1em"><b>sanlock_log_t</b></p>
<p style="margin-left:11%; margin-top: 1em">/var/log/sanlock.log.*</p>
<p style="margin-left:11%; margin-top: 1em"><b>sanlock_var_run_t</b></p>
<p style="margin-left:11%; margin-top: 1em">/var/run/sanlock(/.*)?
<br>
/var/run/sanlk-resetd(/.*)?</p>
<p style="margin-left:11%; margin-top: 1em"><b>user_home_t</b></p>
<p style="margin-left:11%; margin-top: 1em">/home/[^/]+/.+</p>
<p style="margin-left:11%; margin-top: 1em"><b>virt_var_lib_t</b></p>
<p style="margin-left:11%; margin-top: 1em">/var/lib/oz(/.*)?
<br>
/var/lib/libvirt(/.*)?</p>
<h2>FILE CONTEXTS
<a name="FILE CONTEXTS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">SELinux
requires files to have an extended attribute to define the
file type.</p>
<p style="margin-left:11%; margin-top: 1em">You can see the
context of a file using the <b>−Z</b> option to
<b>ls</b></p>
<p style="margin-left:11%; margin-top: 1em">Policy governs
the access confined processes have to these files. SELinux
sanlock policy is very flexible allowing users to setup
their sanlock processes in as secure a method as
possible.</p>
<p style="margin-left:11%; margin-top: 1em"><b>STANDARD
FILE CONTEXT</b></p>
<p style="margin-left:11%; margin-top: 1em">SELinux defines
the file context types for the sanlock, if you wanted to
store files with these types in a diffent paths, you need to
execute the semanage command to sepecify alternate labeling
and then use restorecon to put the labels on disk.</p>
<p style="margin-left:11%; margin-top: 1em"><b>semanage
fcontext -a -t sanlock_var_run_t
’/srv/mysanlock_content(/.*)?’ <br>
restorecon -R -v /srv/mysanlock_content</b></p>
<p style="margin-left:11%; margin-top: 1em">Note: SELinux
often uses regular expressions to specify labels that match
multiple files.</p>
<p style="margin-left:11%; margin-top: 1em"><i>The
following file types are defined for sanlock:</i></p>
<p style="margin-left:11%; margin-top: 1em"><b>sanlock_conf_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the sanlock_conf_t type, if you want to treat the files
as sanlock configuration data, usually stored under the /etc
directory.</p>
<p style="margin-left:11%; margin-top: 1em"><b>sanlock_exec_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the sanlock_exec_t type, if you want to transition an
executable to the sanlock_t domain.</p>
<p style="margin-left:11%; margin-top: 1em"><b>sanlock_initrc_exec_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the sanlock_initrc_exec_t type, if you want to
transition an executable to the sanlock_initrc_t domain.</p>
<p style="margin-left:11%; margin-top: 1em"><b>sanlock_log_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the sanlock_log_t type, if you want to treat the data
as sanlock log data, usually stored under the /var/log
directory.</p>
<p style="margin-left:11%; margin-top: 1em"><b>sanlock_unit_file_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the sanlock_unit_file_t type, if you want to treat the
files as sanlock unit content.</p>
<p style="margin-left:11%; margin-top: 1em"><b>sanlock_var_run_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the sanlock_var_run_t type, if you want to store the
sanlock files under the /run or /var/run directory. <br>
Paths:</p>
<p style="margin-left:18%;">/var/run/sanlock(/.*)?,
/var/run/sanlk-resetd(/.*)?</p>
<p style="margin-left:11%; margin-top: 1em">Note: File
context can be temporarily modified with the chcon command.
If you want to permanently change the file context you need
to use the <b>semanage fcontext</b> command. This will
modify the SELinux labeling database. You will need to use
<b>restorecon</b> to apply the labels.</p>
<h2>COMMANDS
<a name="COMMANDS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>semanage
fcontext</b> can also be used to manipulate default file
context mappings.</p>
<p style="margin-left:11%; margin-top: 1em"><b>semanage
permissive</b> can also be used to manipulate whether or not
a process type is permissive.</p>
<p style="margin-left:11%; margin-top: 1em"><b>semanage
module</b> can also be used to enable/disable/install/remove
policy modules.</p>
<p style="margin-left:11%; margin-top: 1em"><b>semanage
boolean</b> can also be used to manipulate the booleans</p>
<p style="margin-left:11%; margin-top: 1em"><b>system-config-selinux</b>
is a GUI tool available to customize SELinux policy
settings.</p>
<h2>AUTHOR
<a name="AUTHOR"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">This manual
page was auto-generated using <b>sepolicy manpage .</b></p>
<h2>SEE ALSO
<a name="SEE ALSO"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">selinux(8),
sanlock(8), semanage(8), restorecon(8), chcon(1),
sepolicy(8) , setsebool(8)</p>
<hr>
</body>
</html>